Instead of trying to find faulty keys, we stick
to the mechanics we have in place. This way,
we have less false positives.

However, we enforce a certain Bisq version
format, as parsing and business logic relies
on that now.

Turns out, scanning resources does not work reliable enough. Thus,
an array of Strings denoting historical Bisq versions it is.

An other way to put it is it is an array denoting which data stores
are there in the resources.

If we use the diff sync between seed nodes we create a race condition
where when a seednode gets updated to the new system, it does not
sync up properly with the other seed nodes. And that would be fatal.

So for the time being, when a seednode asks for data, it uses the
"old" big requests with all object keys. Should not be a problem
for now since they have enough bandwidth.

CI does have troubles with tests which do file operations. Thus,
these tests have been disabled. They have been useful during
development and are useful for testing locally, though.

This test addresses the migration scenario where a user does not
upgrade on the first possible occation (to the first Bisq version
that has the new database structure in place) but does so later.

Do not clone data anymore as not needed.

Remove unneeded changed checks, remove unused method

…anymore

We do not call persist at each handleComplete of the task runner (each task completion) but at the TaskRunner completion instead.
The tasks should still deal with their own persisting on important data changes. As we persist at shutdown anyway there is not much risk even if some persist calls are missing.

…adeManager instead

We have on case where set the state from inside the trade via setConfirmedState. As the confidence has its listener inside the trade as well this cannot be easily changed. But as when confidence of deposit tx changes we get anyway a outside task triggered and at restart we apply the confidence a confidence anyway so persistence is not really needed. As we persist at shutdown as well we have it covered there as well.
The confidence handling inside the trade should be refactored at some point so that trade does not get overloaded that much with behaviour code. Should be much more a value object....

…eHandler

Rename methods and fields
Return early in method

…ead call readStore direclty.

# Conflicts:
#	common/src/main/java/bisq/common/proto/persistable/UserThreadMappedPersistableEnvelope.java
#	common/src/main/java/bisq/common/storage/FileManager.java
#	p2p/src/main/java/bisq/network/p2p/peers/PeerManager.java

…persistence-model-merged

# Conflicts:
#	common/src/main/java/bisq/common/file/CorruptedStorageFileHandler.java
#	core/src/main/java/bisq/core/account/sign/SignedWitnessStore.java
#	core/src/main/java/bisq/core/account/witness/AccountAgeWitnessStore.java
#	core/src/main/java/bisq/core/dao/governance/blindvote/storage/BlindVoteStore.java
#	core/src/main/java/bisq/core/dao/governance/proposal/storage/appendonly/ProposalStore.java
#	core/src/main/java/bisq/core/trade/statistics/TradeStatistics2StorageService.java
#	core/src/main/java/bisq/core/trade/statistics/TradeStatistics2Store.java
#	p2p/src/main/java/bisq/network/p2p/storage/P2PDataStorage.java
#	p2p/src/main/java/bisq/network/p2p/storage/persistence/AppendOnlyDataStoreService.java
#	p2p/src/main/java/bisq/network/p2p/storage/persistence/PersistableNetworkPayloadStore.java